-
Notifications
You must be signed in to change notification settings - Fork 24
Publishing a module with python dependencies #1021
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
isc-jili
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good! Thanks for fixing this.
Would it be good to add some tests for the publish command with "export-python-deps"? As well as add/edit test cases that demonstrate the previously buggy behavior that were not caught by previous existing tests?
|
Agreed that some tests would be good. Also maybe rename the PR to something more informative? |
| do ..ExportSingleModule(.tSingleModuleArray, pTargetDirectory, .pDependencyGraph, .tParams, tVerbose) | ||
| } | ||
|
|
||
| set exportPythonDependencies = $get(pParams("ExportPythonDependencies"), 0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@isc-jlechtne Does this ensure python dependencies of dependent modules are also exported? It doesn't seem to and only seems to do it for the base module?
Addresses #1024 as well as adding the
-export-python-depsflag to the "publish" command